-
Notifications
You must be signed in to change notification settings - Fork 67
SWIFT-434 Document how to use the driver with TLS/SSL #438
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
kmahar
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks really good! just some small nits
kmahar
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm mod one more nit
Guides/TLS.md
Outdated
| @@ -0,0 +1,81 @@ | |||
| # TLS/SSL and MongoSwift | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
whoops I missed that MongoSwift was used in the title too :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated to "Swift Driver TLS/SSL" guide. Also filed a ticket for updating the various other guides as well
Codecov Report
@@ Coverage Diff @@
## master #438 +/- ##
==========================================
+ Coverage 77.88% 77.94% +0.06%
==========================================
Files 115 115
Lines 12330 12332 +2
==========================================
+ Hits 9603 9612 +9
+ Misses 2727 2720 -7
Continue to review full report at Codecov.
|
SWIFT-434
As the ticket describes, this PR adds documentation for describing how to ensure clients are using the latest TLS protocols. As part of that, figured it made sense to write the rest of the guide, since we didn't already have one. The guide was heavily influenced by pymongo's guide on the same topic.
One API change that's important to note: I added a generic
tlsoption toClientOptions, since it seems reasonable to me that a user would want to enable TLS but not necessarily identify all the client's connecting to the database. This option is included in the URI options spec, and I think most drivers support it (pymongo does at least). cc @mbroadst